The CygNet Historian supports extended historical data of various data types, lengths, and character widths. Each historical entry’s value may contain between 16 and 271 bytes of data. The type of the value data may be specified in UTF8, double, or int64. Each historical entry may optionally contain one BLOB record.
Extensible historical data leverages the infrastructure available in the ESE-based VHS.
The VHS Import/Export utility supports extended entry values.
Extended entry values and BLOB lengths are audited by the AUD. See Service Audit Levels for more information.
VHS service-side security checks include extended entry values. VHS message processing evaluates ACCESS control for names, values and BLOBs. See Value History Service Security for more information.
A .Net API that exposes extensibility features of the CygNet Historian is available. The primary namespace, CygNet.API.Historian, allows for the storage and retrieval of extended data.
The .Net API requires the Microsoft .NET Framework is installed, in accordance with the CygNet System Requirements document.
A standalone online help file CygNet.API.chm is available for user assistance. The API libraries and help file can be found in the /Bin directory on the release image.
|
|
|